…N (12 lines) (#838)

* ops(0-0-0): batch 2 — 8 files SAFE (81 lines) + 1 file NEEDS_HUMAN_DECISION (12 lines)

Promotes 8 of 9 batch-2 candidates to SAFE_TO_RESET_LFG_SUPERSEDES with named per-file evidence; flags 1 file (loop-tick-history.md) as NEEDS_HUMAN_DECISION due to mutual divergence in tick-record content.

Ledger transition (273 = 215 + 12 + 46 ✓):
- classified_safe_lines: 134 → 215 (+81)
- unsafe_lines: 0 → 12 (loop-tick-history.md NEEDS_HUMAN_DECISION)
- unclassified_lines: 139 → 46 (-93)

Batch 2 SAFE files + dominant evidence pattern:
- codeql-config.yml (6): LFG bb0227e + 817e59c + 1e09fef — deliberate paths-ignore decision (java-kotlin matrix, scan AlloyRunner.java) that AceHack reverted
- memory-index-duplicate-lint.yml (8) + audit-memory-index-duplicates.sh (8): persona-name attribution comments on current-state CI/tool surfaces (role-vs-name rule violation); LFG uses role-refs
- Shard.fs (9): LFG aa5395b + 9373755 — perf-fixed non-boxing EqualityComparer<'K>.Default per Copilot P1 review on LFG #649; AceHack still has explicit boxing
- AUTONOMOUS-LOOP.md (9): LFG 8aa4adc — Option B per-tick shard-mode doctrine (PR #724, landed 2026-04-29T02:04:38Z); AceHack describes legacy single-table append
- macos.sh (11): LFG more detailed shellcheck rationale + role-refs; AceHack adds persona-name attribution + terser shellcheck
- fix-markdown-md032-md026.py (16): LFG f57d683 + 515db64 — strict superset (376 lines vs 235), adds YAML frontmatter handling AceHack lacks; fence-detection logic identical
- curl-fetch.sh (14): LFG more accurate retry-math comment ("up to 5 retries (6 total attempts including the initial try, per curl(1))" vs AceHack incorrect "five attempts total") + role-refs vs AceHack persona-name

Batch 2 NEEDS_HUMAN_DECISION (1 file):
- loop-tick-history.md (12): mutual divergence. Each fork has 9-10 unique pre-Option-B tick rows. Maintainer call needed: accept loss / forward-sync / migrate-to-shards. Recommendation: migrate AceHack-only rows to docs/hygiene-history/ticks/2026/04/{21,28}/ shard files (preserves evidence in modern format AND makes file content-identical between forks).

Remaining unclassified after batch 2 (46 lines / 2 files):
- 38 .github/workflows/budget-snapshot-cadence.yml
- 8  memory/project_laptop_only_source_integration_scratch_sqlsharp_features_or_designs_high_priority_2026_04_27.md

Lane discipline preserved per Amara 2026-04-29 review: classify files, reduce unclassified_lines, record named evidence. No LOST recovery, no tick-3 promotion, no gate-runner script.

* hygiene(tick-history): shard 1207Z — 0/0/0 batch-2 classification post computer-restart (#838 opened)

Resume tick after Aaron's computer restart. Recovery sequence: fresh-clone recreated (/tmp wiped on macOS reboot, expected), local main synced to LFG #837 squash-merge, batch-2 evidence re-verified, PR #838 opened with 8 SAFE + 1 NEEDS_HUMAN_DECISION (loop-tick-history.md mutual divergence).

Ledger: 134→215 classified_safe, 0→12 unsafe, 139→46 unclassified. Arithmetic: 273=215+12+46 ✓.

Resume-protocol validated: load-state file (`docs/active-trajectory.md`) prevented audit-spiral after restart; fresh-clone recreation procedure was self-evident from doc text.

* ops(0-0-0): address #838 review threads — scrub persona names from new prose + refresh ledger header

Two real findings from #838 review:

1. Copilot (CLASSIFICATION.md line 114): the new Batch 2 evidence cells contained quoted persona-names ("Amara"/"Aaron") in evidence prose. Even though the names appeared as data being shown to the reader (what AceHack contains), CLASSIFICATION.md is a current-state doc surface and the role-vs-name rule applies. Fix: rewrite the affected cells to describe the wrong-form attribution at meta level (e.g. "persona-name attribution citing an external AI reviewer + a PR number") instead of verbatim-quoting the names being criticized. Pre-existing persona-names elsewhere in the doc were NOT introduced in this PR and are not addressed here (would require the same rule-extension move that landed for active-trajectory.md, which was an explicit maintainer call; no equivalent call exists for CLASSIFICATION.md so I'm not extending).

2. Copilot (active-trajectory.md line 145): the ledger header still said "computed 2026-04-29T11:32Z" — stale relative to the Batch 2 update. Fix: update the header to "last updated 2026-04-29T12:13Z, post-Batch-2", clarify which number is the canonically-computed one (potential_loss_lines = 273, computed 2026-04-29T10:25Z), and explain why it remains canonical (LFG advanced via #837 but only on docs not in the AceHack-vs-LFG file set).

Lane discipline preserved per Amara 2026-04-29 review: classify files, reduce unclassified_lines, record named evidence. No new file classifications added in this commit.

* ops(0-0-0): address #838 Codex P2 — fix mutually-exclusive-bucket violation in loop-tick-history.md cell + record maintainer (c) decision

Codex P2 (12:18Z): the NEEDS_HUMAN_DECISION evidence cell for loop-tick-history.md listed `2026-04-21T17:28` in BOTH the AceHack-only AND LFG-only timestamp buckets, but the buckets were defined as mutually exclusive. The actual git state is: that timestamp's row exists on BOTH forks with content drift in the trailing portion, so it appears as a `+/-` pair in `git diff` rather than as unique-to-one-side.

Fix: rewrite the cell to enumerate three honest cases — truly unique to AceHack (9 timestamps), truly unique to LFG (9 timestamps), and present on both with content drift (1 timestamp: 2026-04-21T17:28).

Also records the maintainer (c) decision (forwarded 2026-04-29 via the multi-AI review packet): migrate AceHack-only rows to per-tick shard files under docs/hygiene-history/ticks/2026/04/{21,28}/, then hard-reset. The cell now notes the file reclassifies to SAFE_TO_RESET_LFG_SUPERSEDES once the option-(c) migration PR lands.

This is a hard-defect fix per Amara's lane caution ("If CI is waiting: ... fix only hard defects if review threads appear"). No new file classifications added; no scope widening.

* ops(0-0-0): address #838 Copilot P1 — revert cell to consistent NEEDS_HUMAN_DECISION state (decision ≠ resolution)

Copilot P1 (12:23Z): the previous cell update conflated "decision exists" with "decision executed". The cell read "NEEDS_HUMAN_DECISION → maintainer chose option (c)", which is config-drift relative to the rest of the PR (active-trajectory.md ledger still has unsafe_lines=12; PR description still treats the file as decision-pending).

Fix: revert the cell to pure NEEDS_HUMAN_DECISION state. The file's classification changes only when option-(c) execution actually lands (the migration PR), not when the decision arrives. Until then the file is "decision-made-but-not-executed" → still NEEDS_HUMAN_DECISION for ledger purposes.

Cell still preserves the precision improvements from the prior fix:
- 3 honest cases (9 truly-unique-AceHack + 9 truly-unique-LFG + 1 same-timestamp-drift)
- explicit note that diff direction is not row identity
- (c) listed as recommended path in the maintainer-decision options

The maintainer-(c) decision will be acted on in a separate post-#838 migration PR. That's where the file's classification flips.